Skip to content

fix(target): put the attempt's module tree on MODULEPATH for verification - #38

Merged
HaoZeke merged 1 commit into
mainfrom
fix/attempt-modulepath
Nov 16, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
fix/attempt-modulepath

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

A verification command runs with the attempt's module tree first on MODULEPATH. The docs say each attempt's --installpath takes precedence over the prefix EESSI-extend derives from EESSI_USER_INSTALL.

  • A campaign attempt builds with --installpath set to its own prefix, <work_root>/install-attempts/<package>-<version>/attempt-<N>. Nothing put the prefix's module tree on MODULEPATH, so a verification command such as module load {module} && ... could not find the module the attempt had just built. On EESSI 2026.06, natsort's verification failed with Lmod's "The following module(s) are unknown".
  • verification_command now runs the command through a short sh wrapper on the target that puts the module tree first on MODULEPATH and on EESSI_EXTRA_MODULEPATH. The EESSI init replaces MODULEPATH and keeps EESSI_EXTRA_MODULEPATH. The tree follows EasyBuild's install_path('mod'), by default <installpath>/modules/all. Without EASYBUILD_INSTALLPATH the command is unchanged. The target reference, the campaign run reference, and the eOn on EESSI how-to now say where attempts install.

a_verification_command_loads_the_module_the_attempt_installed and verification_command_puts_the_installed_module_tree_first cover those. The commit has a towncrier fragment. Main has no towncrier yet; #26 (fix/towncrier) adds it.

…tion

A campaign attempt builds with --installpath set to its own prefix,
<work_root>/install-attempts/<package>-<version>/attempt-<N>, and that
flag takes precedence over the prefix EESSI-extend derives from
EESSI_USER_INSTALL. Nothing put the prefix's module tree on MODULEPATH,
so a verification command such as the examples'
`module load {module} && ...` could not find the module the attempt had
just built. On EESSI 2026.06, natsort's verification failed with Lmod's
"The following module(s) are unknown"; with this change the same
campaign completes and natsort is binary-verified.

verification_command now runs the command through a short sh wrapper on
the target that puts the module tree first on MODULEPATH and on
EESSI_EXTRA_MODULEPATH, extending the values there. The EESSI init
replaces MODULEPATH and keeps EESSI_EXTRA_MODULEPATH, after its own
trees. The tree follows EasyBuild's install_path('mod'):
EASYBUILD_INSTALLPATH_MODULES, or the install path and
EASYBUILD_SUBDIR_MODULES, then EASYBUILD_SUFFIX_MODULES_PATH, by
default <installpath>/modules/all. Without EASYBUILD_INSTALLPATH the
command is unchanged.

The target reference, the campaign run reference, and the eOn on EESSI
how-to now say where attempts install, and the how-to no longer says
the modules land under $EESSI_USER_INSTALL. A campaign test with a fake
eb and a target test of the routed command cover the module tree, with
and without an EESSI-style MODULEPATH reset; both fail without the fix.
@HaoZeke
HaoZeke merged commit 8d8aa84 into main Nov 16, 2026
21 checks passed
@HaoZeke
HaoZeke deleted the fix/attempt-modulepath branch November 16, 2026 05:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant